Tracking issue

#3960

Why are the changes needed?

The current execution tag is a hash tag (key-only tag), but we want to support a key-value tag. The key is required, but the value is optional. That said, you can still use a hash tag by not providing a value.

What changes were proposed in this pull request?

Tables

• Drop execution_admin_tags table
• Drop admin_tags table
• Add execution_tags table

To keep backward compatibility, both labels and tags in the executionSpc will be added to the new execution_tags table.

Endpoint to get the workflows with tags

• Get: http://localhost:30080/api/v1/executions/flytesnacks/development/f6e2ba11a96c24e79a88
• List: http://localhost:30080/api/v1/executions/flytesnacks/development?limit=5
• List with filter: http://localhost:30080/api/v1/executions/flytesnacks/development?filters=value_in(execution_tag.key,flyte%3Btest)&limit=25&sort_by.direction=DESCENDING&sort_by.key=created_at
• List with filter: http://localhost:30080/api/v1/executions/flytesnacks/development?filters=value_in(execution_tag.value,hello%3Brust)&limit=25&sort_by.direction=DESCENDING&sort_by.key=created_at

The old filter still works, and it will get the tag from the new table

• List with filter: http://localhost:30080/api/v1/executions/flytesnacks/development?filters=value_in(admin_tag.name,flyte%3Btest)&limit=25&sort_by.direction=DESCENDING&sort_by.key=created_at

How was this patch tested?

local sandbox

pyflyte run --remote --label tokio=3 --label rust=6 flyte-example/getting_started.py wf
pyflyte run --remote --tag 123 --tag 456 flyte-example/getting_started.py wf 

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

NA

Docs link

NA